-
Notifications
You must be signed in to change notification settings - Fork 693
Conversation
The remaining changes need some changes in |
The |
Ok, this PR should contain the full set of changes now. |
Note to self, update docs to drop |
14d0c74
to
4e896e3
Compare
For users that want to build and transport Docker images without running a Linux-only daemon as root, the Bazel docker rules and Then you'd have the additional advantage over |
@jmillikin-stripe Not exactly the intent of the intermediate format, but I definitely acknowledge the broader sentiment. I will open an issue to track documenting the format on-disk, as well as the intermediate representation in this repo. |
This commit pulls in the latest release of `google/containerregistry`, which includes a new fast-path for puller/pusher to use, which is consistent with our new intermediate format. This commit adapts `docker_pull` to consume the new puller and stitch together the image's constituent elements using `docker_import`. This commit also changes `docker_push` to consume the new options on the new pusher to publish images without linking the full `docker save` tarball, which can be quite expensive for large images.
@dlorenc Anything to add? |
Automatic merge from submit-queue (batch tested with PRs 50889, 51347, 50582, 51297, 51264) bazel: use fast docker_pull **What this PR does / why we need it**: takes advantage of bazelbuild/rules_docker#71. Faster builds = yay. **Release note**: ```release-note NONE ``` /assign @Q-Lee @spxtr @mikedanese
This is a work in progress on top of #70 building tighter integration between
docker_pull
,docker_push
and the new intermediate form ofdocker_build
in the diffbase PR.Right now this just consists of a
docker_import
rule, which will be useful for folks checking in base images to a mono-repo to still get performant builds. It will also be an implementation detail ofdocker_pull
in a subsequent change.For now, I'm simply opening this PR to run CI over my branch :)